Skip to content

Conversation

Fr4nc3
Copy link
Collaborator

@Fr4nc3 Fr4nc3 commented Jan 27, 2025

Purpose

fix the local environment run process that is failing due to missing infra environment variables and incorrect file names

Does this introduce a breaking change?

  • Yes
  • No

How to Test

Steps to Test

  1. Using the Bicep extension for VSCode:

    • Open the .bicep file in VSCode.
    • Right-click the file and select "Show deployment plane".
  2. Using the Azure CLI:
    Run the following command in your terminal:

    az deployment group create -g <resource-group-name> -f deploy/macae-dev.bicep --query 'properties.outputs'
    • Replace <resource-group-name> with the name of your resource group.
    • During the deployment, you will be prompted to provide the following:
      • Principal ID: This is the ObjectID of your user in Entra ID. You can find it by running:
        az ad signed-in-user show --query id -o tsv
      • Locations for Cosmos and Open AI services: This allows deployment in separate regions to address potential service quota restrictions.
  3. Create a .env file:

    • Navigate to the src folder and create a .env file.
    • Use the provided .env.sample file as a template.
  4. Fill in the .env file:

    • Use the outputs from the deployment or check the Azure Portal under "Deployments" in the resource group to retrieve the necessary values.
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install
  • Test the code

What to Check

Verify that the following are valid

  • ...

Other Information

@Fr4nc3 Fr4nc3 closed this Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant